Release 10.1A: OpenEdge Development:
ADM and SmartObjects

Planning issues

Before you use the New ADM Class tool, consider some planning issues for questions that will arise during its use. Be sure to resolve these issues before you use this tool to create your new class:

Decide where to put your new class files at design time. Since an ADM class is a collection of files, most of which are include files, and other files will reference the location of these include files, you might want to have a standard location in which to put all of the new class files. The New ADM Class tool (described later in this chapter) prompts you to enter the name of the directory where you want your new class files to be written. Progress Software Corporation recommends you follow the convention of the standard ADM class files and create an src\adm2 directory for your source files and an adm2 directory for your .r files in your working directory.
Think about how to name your class files. The New ADM Class tool automatically generates the filenames based on the naming convention used for the standard ADM class files shipped with Progress. Progress Software Corporation recommends you use the same convention with your new class files.
The New ADM Class tool automatically creates a custom subdirectory under the source directory you specify. This subdirectory will hold all the custom files or hooks that the standard ADM class files reference to allow the end user to customize the class. These files are a necessary part of the class structure, even if you do not plan to use them.

Remember you cannot change the filenames and relative paths of a class once the AppBuilder generates the files. You must be careful to create a development environment that is consistent with the environment and file structure in which you plan to deploy your applications.